What changed

• add a Discover path that mines scoped codebases and coding-thread history for repeated work
• require concrete recurrence evidence and distinguish potential code patterns from proven repetition
• validate discovered and crafted loops against the full feedback-cycle, verification, stopping, and approval best practices
• document installation, invocation, discovery behavior, outputs, and limitations in the README
• add regression checks for the new skill and documentation contract

Why

Loop Library could find, audit, adapt, and design loops, but it did not have a grounded workflow for discovering loop opportunities from real engineering work.

Validation

• skill package validation
• node scripts/check.mjs
• 41 Worker tests
• git diff --check
• structured autoreview: clean, no actionable findings